Aircraft communications system using whitelists to control access and associated methods

ABSTRACT

A communications system for an aircraft carrying personnel having personal electronic devices (PEDs) includes a wireless access device in the aircraft for the PEDs, and an aircraft server in the aircraft cooperating with the wireless access device for determining airborne validation of a ground server address entered via a corresponding PED. An air-to-ground transceiver in the aircraft cooperates with the aircraft server for communicating over an air-to-ground interface the airborne validated ground server address. A ground server on the ground receives the airborne validated ground server address over the air-to-ground interface, determines ground validation of the airborne validated ground server address, and provides ground access for the corresponding PED for which the entered ground server address has both airborne and ground validation.

RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Ser. No. 61/051,234 filed May 7, 2008, the entire contents of which are incorporated herein by reference.

FIELD OF THE INVENTION

The present invention relates to the field of communications systems, and more particularly, to a communications system for an aircraft having personal electronic devices (PEDs) for communicating outside the aircraft.

BACKGROUND OF THE INVENTION

Existing cellular mobile telecommunication systems serve terrestrial (i.e. ground-based) personal wireless subscriber devices. For discussion purposes, these devices are also referred to as personal electronic devices (PEDs), and include mobile (cellular and PCS) telephones, smart phones, personal digital assistants, wireless email devices, wireless equipped laptop computers, and personal computers. Since the cellular mobile telecommunication systems are terrestrial-based, they are not readily extendable to non-terrestrial applications due to signal interference problems between ground-based and non-terrestrial personal wireless subscriber devices. Moreover, tower antennas supporting the terrestrial-based system are often pointed down to improve performance.

U.S. Pat. No. 7,113,780 assigned to Aircell, Inc. discloses an aircraft-based network for wireless subscriber devices that provides wireless telecommunication services in the aircraft for both terrestrial and non-terrestrial regions. In particular, an air-to-ground network and a ground-based cellular communications network are spoofed into thinking that the wireless subscriber devices have no special considerations associated with their operation, even though the wireless subscriber devices are located on an aircraft in flight. This requires a non-terrestrial feature transparency system on-board the aircraft to replicate the full functionality of a given wireless subscriber device, which has a certain predetermined feature set from a ground-based wireless service provider, at another wireless subscriber device located within the aircraft. This mirroring of wireless subscriber device attributes enables a localized cell for in-cabin communications yet retains the same wireless subscriber device attributes for the air-to-ground link.

Another aircraft-based network for wireless subscriber devices that provided wireless telecommunication services in an aircraft for both terrestrial and non-terrestrial regions was introduced by Boeing, and was referred to as Connexion by Boeing^(SM). Connexion by Boeing^(SM) is no longer in service due to its failure to attract sufficient customers, but at the time, provided an in-flight online connectivity service. This service allowed travelers to access a satellite-based high-speed Internet connection for an hourly or flat rate fee while in flight through a wired Ethernet or a wireless 802.11 Wi-Fi connection. The infrastructure used a phased array antenna or a mechanically steered Ku-band antenna on the aircraft, a satellite link to and from the aircraft, leased satellite transponders, and ground stations.

Even in view of the advances made to aircraft communications systems allowing passengers to operate wireless portable handheld devices while airborne, there is still a need to improve upon this service.

SUMMARY OF THE INVENTION

In view of the foregoing background, it is therefore an object of the present invention to provide an air-to-ground communications system in which personal electronic devices (PEDs) can be operated while in flight for securely communicating with a ground based server.

This and other objects, advantages and features in accordance with the present invention are provided by a communications system for an aircraft carrying at least one person having a PED, wherein the communications system comprises at least one wireless access device in the aircraft, and an aircraft server in the aircraft cooperating with the at least one wireless access device for determining airborne validation of at least one ground server address entered via a corresponding PED. An air-to-ground transceiver in the aircraft may cooperate with the aircraft server for communicating over an air-to-ground interface the at least one airborne validated ground server address. At least one ground server on the ground may receive the at least one airborne validated ground server address over the air-to-ground interface, determine ground validation of the at least one airborne validated ground server address, and provide ground access for the corresponding PED for which the entered at least one ground server address has both airborne and ground validation.

As an example, the ground server address may correspond to an email server address, and the ground server interfaces with an email server so that the PED can securely exchange emails outside the aircraft.

The aircraft server advantageously provides a first level server address validation via algorithms implemented on the aircraft server which are executed through software resident on the aircraft server. Similarly, the ground server advantageously provides a second level server address validation via algorithms implemented on the ground server which are executed through software resident on the ground server. If the ground server address passes the first and second level validations, then the ground server address is declared valid and may be added to a whitelist of accepted ground server addresses.

The wireless access device in the aircraft may comprise an access point for providing a wireless local area network (WLAN) for the PEDs. The ground server may comprise an organization or corporate ground server having a firewall associated therewith, and the ground server address may correspond to the organization or corporate ground server. Each PED may access a web-based prompt via the wireless access device to enter a ground server address. The ground server address may correspond to a uniform resource locator (URL).

In terms of airborne validation, the aircraft server may determine airborne validation of the entered ground server address by comparing to an airborne whitelist of accepted ground server addresses. Alternatively, the aircraft server may determine airborne validation of the entered ground server address by comparing to an airborne blacklist of rejected ground server addresses. The entered ground server address may correspond to a uniform resource locator (URL) or other unique identifier, and the ground server may determine airborne validation by determining if the URL has a valid URL syntax. The server may return an error message to each PED having a ground server address associated therewith that fails airborne validation.

In terms of ground validation, the ground server may determine ground validation of the airborne validated ground server address by comparing to a ground whitelist of accepted ground server addresses. Alternatively, the ground server may determine ground validation of the airborne validated ground server address by comparing to a ground blacklist of rejected ground server addresses. The airborne validated ground server address may correspond to a uniform resource locator (URL) or other unique identifier, and the ground server may determine ground validation by determining if the URL has a valid URL syntax. The ground server may return an error message over the air-to-ground interface for each PED having an airborne validated ground server address associated therewith that fails ground validation.

The server in the aircraft may maintain an airborne whitelist of accepted ground server addresses. The ground server may dynamically update the airborne whitelist over the air-to-ground interface to include the airborne validated ground server address after ground validation. The dynamic updates to the airborne whitelist may be temporary, and may expire at an end of a flight of the aircraft, for example. It may also be possible to keep track of requested ground server addresses to determine if any could be moved from the dynamic category to a preloaded whitelist or preloaded blacklist maintained on either the aircraft server or on the ground server.

Another aspect of the present invention is directed to a method for operating a communications system as described above. The method may comprise operating the PEDs in the aircraft for entering ground server addresses to the wireless access device, and operating the aircraft server in the aircraft to cooperate with the wireless access device for determining airborne validation of at least one email server address entered via a corresponding PED. The air-to-ground transceiver in the aircraft may be operated to cooperate with the aircraft server for communicating over an air-to-ground interface the at least one airborne validated ground server address. The ground server on the ground may be operated to receive the at least one airborne validated ground server address over the air-to-ground interface, to determine ground validation of the at least one airborne validated ground server address, and to provide ground access for the corresponding PED for which the entered at least one ground server address has both airborne and ground validation.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of an air-to-ground communications network in accordance with the present invention.

FIG. 2 is a schematic diagram of another embodiment of the air-to-ground communications network with passenger carried equipment on the aircraft in accordance with the present invention.

FIG. 3 is a schematic diagram of another embodiment of the PED shown in FIG. 2 with the translator device integrated therein.

FIG. 4 is a schematic diagram of the air-to-ground communications network in which predetermined web pages are transmitted over an airport data link for storage on the aircraft in accordance with the present invention.

FIG. 5 is a screen shot from a PED of an interactive map corresponding to the flight path of the aircraft in accordance with the present invention.

FIG. 6 is a screen shot from a PED of an interactive map corresponding to the destination of the aircraft in which different information categories are displayed in accordance with the present invention.

FIG. 7 is a schematic diagram of the air-to-ground communications network in which network selection controllers are used for selecting between satellite or air-to-ground communications in accordance with the present invention.

FIG. 8 is a schematic diagram of the air-to-ground communications network in which hard handoff controllers are used for handing off the aircraft between base stations in accordance with the present invention.

FIG. 9 is a schematic diagram of the different content delivery channels available for distribution to the aircraft passengers in accordance with the present invention.

FIG. 10 is a schematic diagram of the aircraft illustrating the different ranges in which data communications is received in accordance with the present invention.

FIG. 11 is a schematic diagram of an air-to-ground communications network including a corporate email server in accordance with the present invention.

FIG. 12 is a screen display on a passenger's PED for accessing corporate email in accordance with the present invention.

FIG. 13 is a screen display on a passenger's PED for entering the corporate email address for verification in accordance with the present invention.

FIG. 14 is a flow diagram illustrating the steps for a passenger to connect to the corporate email server shown in FIG. 11.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which preferred embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout, and prime notation is used to indicate similar elements in alternative embodiments.

Referring initially to FIG. 1, an air-to-ground communications network 100 will be discussed in which passengers within an aircraft 120 are able to communicate over an air-to-ground interface 200 using their own personal electronic devices (PEDs) 130. PEDs 130 include personal mobile smart phones or telephones (cellular and PCS), personal digital assistants, wireless email devices, wireless equipped laptop computers having Wi-Fi/WiMax capability, air cards, or WiFi equipped MP3 players, for example.

As will be discussed in greater detail below, the air-to-ground communications network 100 may be considered as a data-based network as compared to a terrestrial voice-based network that also supports data. A data-based network supports emails and text messaging without having to specifically take into account the additional requirements (including latency) associated with traditional two-way, full duplex live conversational voice. However, the air-to-ground communications network 100 supports voice capability, as VoIP, and can send multimedia in the form of streaming video, multimedia web surfing, still pictures, music, etc. As a result, hard handoffs may be used between the ground-based base stations 140 as the aircraft 120 is in flight. Soft handoffs are often used for voice-based networks, which negatively impacts the amount of frequency spectrum needed for a handoff.

The air-to-ground network 100 is not constrained to use air interfaces deployed for terrestrial networks. An air interface that is not used for terrestrial networks may be used.

The air-to-ground interface 200 is used to communicate with the ground-based base stations 140. Each base station 140 illustratively interfaces with the public switched telephone network (PSTN) 141 and an Internet service provider (ISP) 142 through a switch 143 for providing email and text messaging services. The PSTN 141 and the ISP 142 are illustrated for only one of the base stations 40. Alternatively, an Internet connection 42 could only be provided and not a PSTN connection 41.

In the United States, for example, there are approximately 100 base-stations 140 positioned to directly support the air-to-ground communications network 100 disclosed herein. This is particularly advantageous since the frequency band of the air-to-ground interface 200 is different than the frequency bands associated with cellular mobile telecommunication systems. In the illustrated example of the air-to-ground communications network 100, the allocated frequency spectrum of the air-to-ground interface 200 is based on a paired spacing of 851 MHz and 896 MHz, with 0.5 MHz available at each frequency.

In contrast, one portion of the radio spectrum currently used for terrestrial wireless communications companies is in the 824-849 MHz and 869-894 MHz bands. PCS is a wireless communications network that operates at a radio frequency of 1.9 GHz. Internationally, other frequencies and bands have been allocated for licensed wireless communications, but they do not operate using the paired spacing of 851 MHz and 896 MHz.

In the illustrated embodiment, equipment has been installed on the aircraft 120 so that the aircraft appears as a hotspot or intranet to the PEDs 130. Nodes or access points 160 are spaced throughout the cabin area of the aircraft 120 providing 802.11 services (i.e., Wi-Fi) or 802.16 services (i.e., WiMax), for example. In addition, access to the network 100 could be through an on-board picocell in which the PEDs 130 communicate therewith using cellular or PCS functions. A picocell is analogous to a Wi-Fi or WiMax access point 160.

The access points 160 are illustratively connected to an on-board server 162 and an air-to-ground transceiver 152. The server 162 includes a data memory cache 155 and a data traffic controller 158. An air-to-ground antenna 154 is coupled to the air-to-ground transceiver 152. An optional control panel 164 is illustratively coupled to the server 162. The data memory cache 155 is for storing common data accessible by the PEDs 130 during flight of the aircraft 120, as well as caching web pages for web browsing by a PED 130. The data memory cache 155 also stores information during hard handoffs between base stations 140 as part of a store-and-forward capability. In addition to the cache memory 155 scheme, the server 162 includes a memory supporting a pass-through scheme, as readily appreciated by those skilled in the art.

The aircraft-based data traffic controller 158 is for selectively allocating data communications channel capacity between the PEDs 130 and the ground-based base stations 140. Selectively allocating data communications channel capacity may also be alternatively or additionally performed on the ground using a ground-based data traffic controller 148 coupled to the PSTN 141 and the ISP 142. The respective controllers 148, 158 control the IP traffic that will be allowed over the air-to-ground network 200.

The respective controllers 148, 158 thus operate as filters, which may be static or dynamic. Their operation depends on whether the network 100 is lightly loaded or heavily loaded. For example, an email (from the aircraft 120) with a very large attachment would be limited or restricted by the aircraft-based data traffic controller 158, whereas an Internet request resulting in a large number of web pages being sent to a PED 130 (from a ground-based base station 140) would be limited by the ground-based data traffic controller 148.

By selectively allocating the data communications channel capacity, a greater or maximum number of passengers on the aircraft 120 can communicate over the air-to-ground interface 200 using their own PEDs 130. For a given PED 130, the aircraft-based data traffic controller 158 may thus limit data communications from exceeding a predetermined portion of the data communications channel capacity.

Allocation of the data communications channel capacity may be based on a number of different factors or metrics. For example, the respective data traffic controllers 148, 158 may allocate the data communications channel capacity based on a priority of service. For example, credit card information used for on-board purchases/shopping could have a higher priority over email. The data communications may comprise flight operational data and non-flight operational data. Certain types of traffic may have priority over other types of traffic. Personnel having PEDs 130 include passengers, as well as other individuals supporting operation of the aircraft. Personnel with PEDs 130 supporting operation of the aircraft would be associated with flight operational data, and this may be assigned a higher priority.

PEDs 130 that are cellular or PCS devices and are also Wi-Fi compatible are known as dual-mode devices. One of the modes is cellular communications, with the other mode being Wi-Fi communications. Many laptop, personal computers, and PDAs are Wi-Fi/WiMax compatible, which are also classified herein as PEDs. After a connection is made to the on-board server 162 via Wi-Fi or WiMax, each PED 130 can transmit and receive emails and text messages over the air-to-ground interface 200.

The dual-mode PEDs 130 carried by the passengers thus support multiple air interfaces, i.e., a terrestrial network and Wi-Fi or WiMax. Example terrestrial networks include any one of the following: 1) PCS, 2) the GSM family including EDGE, GPRS, HSDPA, HSUPA, and 3) the CDMA family including IS-95, CDMA2000, 1×RTT, EVDO. The terrestrial network may also operate based on other network interfaces standards, as will be readily appreciated by those skilled in the art. To reduce the cost of the dual-mode PEDs 130, a software radio may be used wherein the radio is configured to the air interface standard that is available. If more than one air interface standard is available, different metrics may be evaluated to determine a preferred air interface.

Referring now to FIGS. 2 and 3, as an alternative to aircraft installed equipment, a respective translator device 50 may be used to interface between each PED 30 and a ground-based base station 40 over the air-to-ground interface 20. The translator device 50 comprises an air-to-ground transceiver 52 with an air-to-ground antenna 54 coupled thereto.

In the illustrated embodiment, no additional equipment may need to be installed in the aircraft 12 since the translator devices 50 would be brought on-board by the passengers. Each translator device 50 may interface with the PED 30 via a wired or wireless connection. The wireless connection may be a Wi-Fi connection (802.11) or a WiMax connection (802.16), for example. The wired connection may be a USB interface 55.

Alternatively, the translator device may be integrated directly into the PED 30′, as illustrated in FIG. 3. The PED 30′ would further include a controller 56′ for selecting between the ground-based transceiver 58′ or the air-to-ground transceiver 52′ associated with the translator. A separate antenna 59′ is coupled to the ground-based transceiver 58′. Instead of separate antennas 54′ and 59′, a shared antenna may be used. The controller 56′ may perform the selection automatically based on one or more monitored metrics, or the selection may be based on input from the user.

Referring again to FIG. 1, another aspect of the illustrated embodiment is directed to a method for operating a communications system 100 for an aircraft 120 carrying at least some personnel having PEDs 130 for wireless data communications outside the aircraft with a ground-based communications network. The communications system 100 includes an access point 160 in the aircraft 120 for providing a WLAN for data communications with the PEDs 130, and an air-to-ground transceiver 152 in the aircraft 120 cooperating with the access point 160 for data communications with the ground-based communications network. The method may comprise selectively allocating data communications channel capacity between the PEDs 130 and the ground-based communications network using at least one data traffic controller. The at least one data traffic controller may be an aircraft-based data traffic controller 158 and/or a ground-based data traffic controller 148.

Referring now to FIG. 4, another aspect will be discussed with respect to the data memory cache 155 cooperating with the access point 160 for storing common data accessible by the PEDs 130 during flight of the aircraft 120. The common data may be in the form of web pages in which passengers can browse via their PED 130.

One of the functions of the data memory cache 155 is for caching predetermined web pages to be browsed. Instead of the aircraft 120 receiving the web pages while in-flight, the web pages are received while the aircraft is on the ground. Nonetheless, the web pages may be alternatively or additionally updated or refreshed while in flight. As an alternative to the data memory cache 155, streaming video or audio could be real time or stored as provided from a satellite, including via a preexisting satellite based IFE system on the aircraft 120.

The stored web pages may be directed to a particular topic or theme, such as services and products. The services may also be directed to advertisements, for example. A purchase acceptance controller 190 cooperates with the WLAN to accept a purchase from the PESs 130 responsive to the common data related to the services and products.

For example, the web content may be directed to an electronic retail supplier so that any one of the passengers on-board the aircraft 120 can shop for a variety of different items using their PED 130. Once a passenger selects an item for purchase, the transaction can be completed in real time while being airborne via the purchase acceptance controller 190 communicating over the air-to-ground link 200. This form of on-board shopping may also be referred to as air-commerce. Alternatively, the transaction could be initiated on-board the aircraft 120 via the purchase acceptance controller 190 but the actual purchase could be forwarded via the ground data link 174 once the aircraft 120 is on the ground.

The data memory cache 155 may be configured to push the common data related to the services and products to the PEDs 130. Also, the data memory cache 155 may permit the PEDs 130 to pull the common data related to the services and products therefrom.

In addition to products and services, the common data is directed to interactive maps, as will now be discussed in reference to FIGS. 5 and 6. When an interactive map is displayed on a POD 130, the passenger is able to scroll or zoom in and out using a scroll or zoom bar 201, as illustrated by the screen shot 203 from their PED 130. The interactive maps preferably correspond to the flight path 203 of the aircraft 120, and are updated or refreshed via the ground data link 174 when the aircraft 120 is parked on the ground at the airport 170.

While in flight, the current location of the aircraft 120 can be displayed. Flight information 205 may also be displayed. The current location of the aircraft 120 may be provided by a position determining device/flight path determining 191, such as a GPS system carried by the aircraft. Alternatively, the position of the aircraft 120 can be determined on the ground and passed to the aircraft over the air-to-ground link 200. The final destination of the aircraft 120 can also be displayed prior to arrival at the destination. In addition, destination information such as the arriving gate number, connecting gate numbers, baggage claim information, hotels, rental car agencies, restaurants, etc. could also be displayed.

Data associated with the destination 209 may also be made available to the passengers. As illustrated by the screen shot 207 from a PED 130, data categories titled Hotels 211, Rental Cars 213, Restaurants 215 and Entertainment 217 are available for viewing by the passenger.

If the passenger does not already have a hotel reservation, then a desired or preferred hotel associated with the destination of the aircraft 120 can be selected from the Hotels category 211. The communications system 100 advantageously allows the passenger to make a hotel reservation while in flight. Likewise, a rental car reservation can also be made while in flight if a car is needed. Other points of interest or services (such as restaurants and entertainment) associated with the destination of the aircraft 120 can also be made available to the passengers, including reservations, coupons and other available discounts, for example.

Referring back to FIG. 4, when the aircraft 120 is parked on the ground at the airport 170, a wireless airport data link 172 is used to transmit the web content pages to the data memory cache 155 via a ground data link receiver 174 carried by the aircraft 120. A ground data link antenna 176 is coupled to the ground data link receiver 174. The ground data link Interface 180 may be compatible with 802.11 or 802.16, for example. The ground data link interface 180 may be Wi-Fi or WiMax for the aircraft 120. Other interface standards may be used as will be readily appreciated by those skilled in the art. These interfaces also include cellular and PCS compatibility, for example.

When the aircraft 120 lands at a different airport, the web pages can be updated or refreshed over the ground data link interface 180. In addition, email and text messaging by the PEDs 130 may be continued after the aircraft is on the ground. Since the air-to-ground interface 200 may not be available when the aircraft 120 is on the ground, the ground data link interface 180 would then be used.

Once the web pages are stored in the data memory cache 155, a passenger using their Wi-Fi or WiMax enabled PED 130 can access and browse the web pages for on-board shopping while the aircraft 120 is airborne. The data memory cache 155 is sufficiently sized for storing a large amount of information, as will be readily appreciated by those skilled in the art.

The on-board shopping just described is for items that are not carried on the aircraft 120. On-board shopping may also be provided to the passengers for a limited number of products. For example, when watching a movie or listening to music, passengers have the option of receiving standard headphones or they can purchase a different set of headphones, such as high quality noise suppression headphones. These transactions can also be completed via the passenger's PED 130 using the web-based pages stored in the data memory cache 155.

Another aspect of the illustrated embodiment is directed to a method for operating a communications system 100 for an aircraft 120 carrying at least some personnel having personal electronic devices (PEDs) for wireless data communications outside the aircraft with a ground-based communications network. The communications system 100 may include an access point 160 in the aircraft 120 for providing a wireless local area network (WLAN) for data communications with the PEDs 130, and an air-to-ground transceiver 152 in the aircraft 120 cooperating with the access point 160 for data communications with the ground-based communications network. The method may comprise storing common data accessible by the PEDs 130 during flight of the aircraft 120 using an aircraft data memory cache 155 in the aircraft and cooperating with the access point 160.

The PEDs 130 are not limited to receiving and transmitting information over the air-to-ground interface 200. Referring now to FIG. 7, signals may be transmitted from satellites 220, 230 to one or more satellite antennas 240 coupled to a satellite receiver 242 carried by the aircraft 120. If there are multiple satellite antennas, then a network selection controller 192 may be used to select the appropriate satellite antenna. This is in addition to transmitting and receiving signals over the air-to-ground interface 200 via the ground-based network and the air-to-ground transceiver 152 carried by the aircraft 120.

In the illustrated embodiment, an aircraft-based network selection controller 192 is associated with the air-to-ground transceiver 152 and the access points 160. The aircraft-based network selection controller 192 determines whether data communications should be sent to the PEDs 130 through the air-to-ground transceiver 152 or the satellite receiver 242. This is accomplished by appending data to return via a satellite.

In addition or in lieu of the aircraft-based network selection controller 192, a ground-based network selection controller 194 is coupled between a ground-based satellite transmitter 145 and the ground-based base stations 140. The ground-based network selection controller 194 also determines whether to send data communications to the PEDs 130 through the air-to-ground transceiver 152 or through the satellite receiver 242.

Satellite 220 provides television and digital radio signals for an in-flight entertainment (IFE) system on the aircraft 120 over satellite link 254. Even though only one satellite is represented, the television and digital radio signals may be provided by separate satellites, such as a DirectTV™ satellite and an XM™ radio satellite. In addition, a third satellite may be used to provide email and text messaging, multimedia messaging, credit card transactions, web surfing, etc. The illustrated satellite antenna 240 supports communications with all three satellites. Alternatively, there may be a separate satellite antenna for the DirectTV™ satellite, the XM™ radio satellite, and the email-text messaging satellite.

An example IFE system is disclosed in U.S. Pat. No. 7,748,597. This patent is assigned to the current assignee of the present invention, and is incorporated herein by reference in its entirety. The television and digital radio signals are sent through the on-board server 162 to seat electronic boxes (SEBs) spaced throughout the aircraft for selective viewing on video display units (VDUs). Passenger control units (PCUs) are used to control the VDUs. The digital radio signals are also distributed to the SEBs for reception via passenger headphones.

Of particular interest is that additional information can be obtained from the satellite 220 which can then be made available to the PEDs 130. For example, the satellite 220 may provide information including sports scores, stock ticker, news headlines, destination weather and destination traffic. The satellite signals received by the satellite receiver 242 are provided to the on-board server 162 for repackaging this particular information for presentation to the PEDs 130 via the access points 160, as will be readily appreciated by those skilled in the art.

When available, satellites with or without leased transponders may also provide additional information to be repackaged by the on-board server 162. The other satellite 230 may be a fixed satellite service (ESS) for providing Internet access to the PEDs 130, for example. For example, satellite television and satellite radio signals may be provided to the passengers on their PEDs 130 via Wi-Fi.

In this configuration, a message for web pages requested by the passenger (via their PED 130) is provided over the air-to-ground interface 200. The message on the ground would then be routed to an appropriate ground-based network selection controller 194, which would then transmit the request to the FSS satellite 230. The satellite link between the appropriate ground-based transmitter 145 and the satellite 230 is represented by reference 250. The SS satellite 230 then transmits the requested web pages to the aircraft 120 over satellite link 252 upon receiving the request from the ground.

Since the satellites may be somewhat close together in a geospatial arc, transmitting the return link over the air-to-ground link 200 instead of over the satellite links 252, 254 avoids causing interference from the aircraft 120 to neighboring satellites. Nonetheless, the request could be transmitted directly from the aircraft 120 to the satellite 230 using a steerable or directional satellite antenna.

The request provided by the PED 130 is often referred to as the return link. The information from the satellites 220, 230 to the aircraft 120 is often referred to as the forward link. The air-to-ground interface 200 is a narrow band interface, which is acceptable for making a request since such a request is typically narrower band than the forward link. In contrast, satellite links 252 and 254 are wide band interfaces, which are ideal form providing the requested web pages that are typically wide band data.

Each of the network selection controllers 192, 194 may be used to determine whether to send data communications to the PEDs 130 through the air-to-ground transceiver 152 or the satellite receiver 242 based on a needed channel capacity of the data communications to be sent or congestion on a link. Data communications with a higher needed channel capacity is typically sent with a high bandwidth using the satellite receiver 242, and data communications with a lower needed channel capacity is typically sent with a low bandwidth using the air-to-ground transceiver 152. Alternatively, the high and low broadband data communications links may be reversed. Alternatively, the network controllers could determine that the aircraft 120 is out of the coverage area for the air-to-ground network or the air-to-ground network is at capacity in the location for that aircraft. In this case, the network selection controllers could route the traffic over the satellite network. Alternatively, the network selection controllers could route some traffic types over one network and other traffic types over the other network, as readily appreciated by those skilled in the art.

One of the network selection controllers 192, 194 may determine to send data communications to the PEDs 130 through the air-to-ground transceiver 152 or through the satellite receiver 242 based on received signal strength of the data communications, or a position of the aircraft. The current location of the aircraft 120 may be provided by a position determining device/flight path determining 191, such as a GPS system carried by the aircraft. Alternatively, the position of the aircraft 120 can be determined on the ground and passed to the aircraft over the air-to-ground link 200. If the aircraft 120 is to fly over the ocean, then data should be received through the satellite receiver 242. By monitoring signal strength of the received signals or the position of the aircraft, a determination can be made on when the ground-based base stations 140 are no longer available, and communications should be received via the satellite receiver 242.

The network selection controllers 192, 194 thus determine whether to send static and dynamic web pages through the satellite-based communications network 145, 230 to the PEDs 130. Dynamic web pages include streaming video, for example. Each network selection controller 192, 194 may determine to send requests for at least one of the static and dynamic web pages from the PEDs 130 through the access points 160 and the air-to-ground transceiver 152.

As noted above, predetermined web pages are stored in the data memory cache 155 when the aircraft 120 is parked on the ground (i.e., electronic retailer shopping and on-board shopping, as well as advertisements). Since the satellite links 252, 254 are wide band, the requested web information may also be downloaded for storage or refreshed in the data memory cache 155 while the aircraft is in flight.

Another aspect of the illustrated embodiment is directed to a method for operating a communications system 100 for an aircraft 120 carrying at least some personnel having personal electronic devices (PEDs) 130 for wireless data communications outside the aircraft. The communications system 100 includes a ground-based communications network, a satellite-based communications network, and at least one access point 160 in the aircraft 120 for providing a WLAN for data communications with the PEDs 130. An air-to-ground transceiver 154 in the aircraft 120 may cooperate with the at least one access point 160 for data communications with the ground-based communications network, and a satellite receiver 242 in the aircraft may cooperate with the at least one access point for data communications with the satellite-based communications network to the PEDs. The method includes determining whether to send data communications to the PEDs 130 through the air-to-ground transceiver 152 or the satellite receiver 242.

Referring now to FIG. 8, another aspect is directed to handoff of the aircraft 120 from one ground-based base station 140 to an adjacent ground-based base station, or between azimuth or elevation sectors on one base station. Since the air-to-ground network 100 may be optimized for data instead of voice, delays or latencies can be tolerated without the end user having the perception that the call is being dropped as is the case with voice. Consequently, soft handoffs are needed for voice-based networks.

In contrast, data can be stored on the ground or on the aircraft while the aircraft 120 is between cell coverage areas for a hard handoff. Once the aircraft 120 is within coverage of the next cell, the data can then be forwarded.

Hard handoffs can thus be used to make the connection from one base station 140 to an adjacent base station in support of the air-to-ground communications network 100. Messages being communicated between a PED 130 and the ground can be stored in a buffer or memory 157. The buffer 157 may be part of the data memory cache 155, or alternatively, the buffer may be a separate memory as illustrated. Each base station 140 has a hard handoff controller 147 associated therewith. Moreover, with the aircraft 120 typically flying at speeds over 500 mph, the delay is relatively short.

To support a soft handoff, as would be necessary with voice, twice the spectrum resources would be needed. With a hard handoff, the spectrum is preserved at the expense of having sufficient memory for storing data in the buffer 157 (or on the ground) during a handoff while the aircraft 120 is between base stations 140.

The base stations 140 define respective adjacent coverage areas and comprise respective hard handoff controllers 147 for implementing a hard handoff of a data communications channel with the air-to-ground transceiver 152 as the aircraft 120 moves from one coverage area to an adjacent coverage area.

An aircraft hard handoff controller 149 may cooperate with the hard handoff controllers 147 on the ground. The aircraft hard handoff controller 149 cooperates with ground-based hard handoff controllers 147 by monitoring metrics. The metrics include a received signal strength of the data communications channel, or available capacity at the base station 140, for example.

In another embodiment for implementing an aircraft hard handoff, the aircraft hard handoff controller 149 implements the hard handoff of a data communications channel with the air-to-ground transceiver 152 as the aircraft 120 moves from one coverage area to an adjacent coverage area. This implementation may be based on metrics collected in the aircraft. These metrics include a Doppler shift of the data communications channel, a signal-to-noise ratio of the data communications channel, or a received signal strength of the data communications channel. This implementation may also be based on position of the aircraft 120, as readily appreciated by those skilled in the art.

The buffer 157 may be separate from the aircraft hard handoff controller 149 or may be integrated as part of the hard handoff controller. The first and second hard handoff controllers 147 may implement the hard handoff based on the following metrics: a Doppler shift of the data communications channel, a signal-to-noise ratio of the data communications channel, or a received signal strength of the data communications channel, as will be readily appreciated by those skilled in the art.

In other embodiments, a position/flight determining device 191 on the aircraft 120 cooperates with the ground-based hard handoff controllers 147 for implementing the hard handoff based upon a position of the aircraft. The position/flight path determining device 191 may be a GPS or other navigational device.

The base stations 140 may be configured with selectable antenna beams for performing the hard handoff, as will now be discussed. In one embodiment, one or more of the base stations 140 include selectable antenna beams 97, with each antenna beam having a same pattern and gain but in a different sector as compared to the other antenna beams. The different sector may also be defined in azimuth and/or elevation. Each antenna beam 97 may be optimized in terms of gain and beam width. The minimally overlapping antenna beams 97 thus provide complete coverage in the different sectors.

In another embodiment, one or more of the base stations 140 include selectable antenna beams 98 and 99, with at least two antenna beams being in a same sector but with a different pattern and gain. Antenna beam 99 is high gain with a narrow beam width for communicating with the aircraft 120 at an extended distance from the base station 140. When the aircraft 120 is closer in range to the base station 140, antenna beam 98 is selected, which is low gain with a wide beam width.

As noted above, there are a number of different metrics to monitor to determine when airborne users (i.e., PEDs 130) within an aircraft 120 are to be handed off to a next base station 140. In terms of Doppler, the Doppler shift on the MAC addresses of the signals received by each base station 140 are examined. The Doppler metric is to be factored into the handoff algorithm at each base station 140.

When using GPS coordinates, each base station 140 receives GPS coordinates of the aircraft 120, and based upon movement of the aircraft, the base stations coordinate handoff of the aircraft accordingly from base station to base station.

Along the same lines, sectorized antennas at the base station 140 may be used for communicating with the aircraft 120. The antennas at each base station 140 may provide a high gain/narrow beamwidth coverage sector and a low gain/broad beamwidth coverage sector. The high gain/narrow beamwidth coverage sector may be used when link conditions with the aircraft 120 are poor. Sites could be sectorized in azimuth, elevation or both. These sectors could be static or dynamic.

If the link conditions with the aircraft 120 are good, then the low gain/broad beamwidth coverage beam is used. In one embodiment, the coverage sectors are selected based upon the link conditions with the aircraft 120. Alternatively, the coverage sectors are fixed at the base station 140. For example, the high gain/narrow beamwidth coverage sector may be used for aircraft 120 that are farther away from the base station 140, whereas the low gain/broad beamwidth coverage sector may be used for aircraft flying near the base station.

Lastly, a ground selection algorithm may be used to select a ground-based base station 140 based on the flight path and the base stations in proximity to the flight path. If the aircraft 120 is about to exit a cell, transmitted email and text messages for a PED 130 are stored until the aircraft is in the next coverage area. This advantageously allows a longer continuous connection, which makes use of the limited spectrum resources more efficiently. The ground selection algorithm could use ground-based location information or GPS data on the location of the aircraft 120 and known ground site locations to optimize connection times. The resulting system may thus be considered a store-and-forward architecture.

Another aspect of the illustrated embodiment is directed to a method for operating a communications system 100 for an aircraft 120 carrying at least some personnel having personal electronic devices (PEDs) 130 for wireless data communications outside the aircraft with a ground-based communications network. The communications system 100 includes a plurality of spaced apart base stations 140, and at least one access point 160 in the aircraft 120 for providing a wireless local area network (WLAN) for data communications with the PEDs 130. An air-to-ground transceiver 152 in the aircraft 120 may cooperate with the at least one access point 160 for data communications with the ground-based communications network. The method may include operating first and second base stations 140 to define respective first and second adjacent coverage areas, with the first and second base stations comprising respective first and second hard handoff controllers 147. The respective first and second hard handoff controllers 147 are operated for implementing a hard handoff of a data communications channel with the air-to-ground transceiver 152 as the aircraft 120 moves from the first coverage area to the second adjacent coverage area. Alternatively, the handoff decision can be implemented by an aircraft hard handoff controller 149 in the aircraft 120. This implementation may be based on metrics collected in the aircraft 120.

To summarize example on-board content deliveries to the aircraft 120 from the various sources, reference is directed to FIG. 9. When in flight, the air-to-ground interface 200 provides connectivity for features that include email, text messaging, credit card transactions, multimedia messaging, web surfing and RSS as indicated by reference 300. To use RSS, the PED 130 has an RSS news reader or aggregator that allows the collection and display of RSS feeds. RSS news readers allow a passenger to view the service selected in one place and, by automatically retrieving updates, stay current with new content soon after it is published. There are many readers available and most are free.

The airport data link 172 may be used to provide the best of YouTube™ as indicated by reference 302. The XM™ satellite 220 may provide sports scores, stock ticker, news headlines and destination traffic as indicated by reference 304. DirectTV™ may also be provided by satellite 220 which can be used to provide additional information as indicated by reference 306. For future growth, two-way communications may be provided by a satellite as indicated by reference 308, such as with DirecWay or Hughesnet, for example. The airport data link 172 may also be used to provide cellular/PCS/WiMax services as indicated by reference 310.

The above content is provided to the on-board server 162 which may include or interface with the data memory cache 155. The data is provided to passenger PEDs 130 using Wi-Fi or WiMax distribution via the access points 160. Video and data is provided to an Ethernet distribution 320 for distributing throughout the aircraft as part of the in-flight entertainment system.

In terms of transmission distance or proximity to the aircraft 120 for the above-described on-board content deliveries, reference is directed to FIG. 10. Circle 350 represents information provided by the airport ground data link 172 when the aircraft 120 is parked at the airport 170 or moving about the airport with weight on wheels. When airborne, circle 352 represents information provided via the air-to-ground interface 200, and circle 354 represents the information provided by the satellites 220, 230. The information as discussed above is summarized in the respective circles 350, 352 and 354.

In view of the different air interface standards associated with the aircraft 120, the on-board server 162 may be configured to recognize the available air interface standards. As a result, the on-board server 162 selects the appropriate air interface standard based on proximity to a particular network. This decision may also be based on the bandwidth that is available, location of the aircraft 120 as determined by GPS, and whether the aircraft is taking off or landing. For example, when the aircraft 120 is on the ground, the ground data link interface 180 is selected. When airborne, the network selection controllers 192, 194 select either the air-to-ground interface 200 or a satellite interface 252, 254 depending on traffic demands, or both, for example.

Depending on the airline rules and regulations, the cellular mode of a dual mode cellular/Wi-Fi device may not be operated on an aircraft below a certain altitude, such as 10,000 feet. To support this requirement, the on-board server 162 and the Wi-Fi access points 160 may have enough picocell capability to drive the cellular radio in dual mode devices to minimum power or even to turn the cellular radios off. The connection to the wireless onboard network could be WiFi or WiMax. The picocell function would be to drive cellular/PCS output power to a reduced/minimum or off condition. This turns the cellular/PCS transmitter “off” while on the aircraft, while allowing Wi-Fi transmission and reception.

Another metric to monitor on the aircraft 120 is related to priority of service. This is due to the fact that that aircraft 120 can receive information over a wide band link from a satellite, for example, and transmit requests for the information over a narrow band link. If someone tries to send a large attachment on their email over the narrow band link, or they are video/audio streaming, then access will be denied or throttled or charged for a premium service for large data transfers by the data traffic controllers 158, 148. It could also be possible to use picocells to connect cellular/PCS mobile phones (PED) 130 to the onboard systems.

Thereforer traffic is monitored in terms of metrics to make quality of service and priority of service decisions. This decision may be made on-board the aircraft 120 for any traffic leaving the aircraft 120. This decision may also be made on the ground, which monitors if someone on the ground is sending to large of an attachment, and if so, then access will also be denied or throttled or charged for a premium service for large data transfers. These criteria for decisions could by dynamic or static.

Priority of service also relates to quality of service. Various metrics and traffic conditions can be monitored to provide connectivity to a greater or maximum number of airline passengers on a flight. Operations and cabin passenger entertainment (email, text messaging, web browsing, etc.) data can be multiplexed on a variable latency link. Operational and passenger data may also be multiplexed with multiple priorities of service allowing some data to be handled at a higher priority than other data.

Yet another aspect of the aircraft air-to-ground communications network 10 is with respect to advertisements. The advertisements are used to generate revenue from the air to ground, hybrid air to ground/satellite, or satellite communications network. For example, when a passenger opens up their laptop computer 130 on the aircraft 120, a decision is made whether or not to use the 802.11 Wi-Fi or 802.16 WiMax network. If the decision is yes, then an advertisement is displayed while accessing the network.

In addition, when portal pages are viewed, advertisements will also be displayed. Since the advertisements are used to generate revenues, passengers are allowed access to the air-to-ground communications network 100 without having to pay with a credit card or touchless payment method, as was the case for the Connexion by Boeing^(SM) system. While looking at different web pages, the passengers will see advertisements interspersed or sharing the same screen.

Another function of the aircraft 120 is to use the air-to-ground communications network 100 for telemetry. Telemetry involves collecting data at remote locations, and then transmitting the data to a central station. The problem arises when the data collection devices at the remote locations are separated beyond line-of-sight from the central station. Consequently, one or more towers are required to complete the telemetry link. To avoid the costly expense of providing telemetry towers, the aircraft 120 may be used to relay the collected information from the remote locations to the central station when flying overhead.

Yet another function of the aircraft 120 is to use the air-to-ground communications network 100 for ground-based REID tracking. Similar to using the aircraft 120 for telemetry, the aircraft may also be used for tracking mobile assets on the ground, such as a fleet of trucks, for example. The trucks transmit REID signals that are received by the aircraft 120 as it flies overhead. The information is then relayed to a central station. The RFID signals may be GPS coordinates, for example.

Another aspect of the air-to-ground communications network 100 is to provide video on demand on the aircraft 120. This feature has been partially discussed above and involves providing television signals on demand to passengers on the aircraft. The television signals may be terrestrial based or relayed via a satellite. In particular, the return to make the request is not the same as the forward link providing the video. The return link is a low data rate link, and may be provided by the aircraft passenger's PED 130 over the air-to-ground interface 200. The forward link is a high data rate link received by a terrestrial or satellite based receiver on the aircraft. The video is then routed through the aircraft in-flight entertainment system to the passenger, or to the passenger's PED 130 via Wi-Fi. Alternatively, the video or audio can be stored in the server 162 and displayed when requested by a passenger.

Yet another aspect of the air-to-ground communications network 100 is to provide a secure network for exchanging data traffic, including but not limited to emails, between a PED 130 carried by a passenger on the aircraft 120 and computer terminals 146 operating within a company/organization or corporation 148, as illustrated in FIG. 11. Even though this aspect of the invention is illustrated for an airborne platform 120, the illustrated communications system could also be adapted to ground-based platforms and water-based platforms for providing a secure network for exchanging data traffic.

Voice may also be transferred as data using voice over Internet protocol (VoIP)+To simplify the figure, a single computer terminal 146 is illustrated. Although not illustrated, the email server 147 servers other computer terminals 146 on the ground, as readily appreciated by those skilled in the art. The secure network is more bandwidth efficient then a virtual private network (VPN) since industry required signaling associated with a VPN is not required. Each computer terminal 146 interfaces with the corporate email server 147, as well as with the ground server 149.

Also in the illustrated embodiment, a ground server 149 is between the air-to-ground interface 200 and the email server 147. The ground server 149 is used in verification of the corporate email server address, as will be described below. Alternatively, the email server 147 may interface directly with the air-to-ground interface 200 to perform verification of the corporate email server address.

In addition to the computer terminals 146, employee carried PEDs may be used to interface the corporate email server 147. An example corporate email server is a Microsoft™ 2003 or 2007 server.

Access to the corporate email server 147 is controlled based on dynamic whitelisting. A whitelist is a list of accepted servers that a communications system defines as acceptable to connect to based on a set of static or dynamic rules. The set of static or dynamic rules are based on allowed email addresses, URLs, domains and/or IP addresses. As readily understood by those skilled in the art, a whitelist is the opposite of a blacklist.

Normally, a passenger would enter their corporate web mail URL syntax in a browser address bar displayed on their PED 130 to access the corporate email server 147. To provide a secure connection, the air-to-ground communications network 100 now verifies the corporate email server address while in the air and on the ground before accessing the corporate email server 147.

To start the verification, the user directs their Internet browser to a corporate email prompt 402 on a home page 400 of the air-to-ground communications network 100, as illustrated in FIG. 12. Of interest, the user also has the option to select other prompts on the illustrated home page 400 in addition to the corporate email prompt 402. These other prompts include, for example, sending other (i.e., non-secure) email 404, accessing other email providers 406 such as Yahoo™, and accessing an on-line company such as Amazon.com™ 408 that sells goods over the Internet.

Referring now to FIG. 13, the displayed screen 410 provides a corporate email prompt 412 that contains a web form entry box in which the user types the address to their corporate webmail URL. The corporate email prompt 412 is also referred to as a corporate email portal. After pressing the submission prompt 414, the system attempts to verify the legitimacy of the server address entered before any data is forwarded over the air-to-ground link 200.

In the illustrated air-to-ground link 200, the interface is directly between the aircraft 120 and the ground server 149. The secure network may also be provided over a satellite link, where the satellite interfaces between the aircraft 120 and the ground server 149.

Verification of the server address that was entered by the passenger via their PED 130 will now be discussed with reference to the flow chart illustrated in FIG. 14. From the start (Block 500), the passenger connects to the corporate email portal 412 at Block 502 and enters their corporate email server address in web form (i.e., a URL syntax) at Block 504.

At a decision block (Block 506), the URL syntax is validated by the on-board server 162. This corresponds to the air validation component of the whitelisting. Before any data is forwarded over the air-to-ground link 200, the URL syntax is verified against one or more tests performed on the aircraft 120 by the on-board server 162. If any of the tests fail, the passenger is presented with an error message at Block 508. One example test is to determine if the corporate email server address is already on the whitelist (if so the request is approved/validated). Other tests include determining if the RDL link is up, is the URL on the Blacklist (if so the request is rejected), and if there is a valid URL syntax. Yet another test is to determine if the ground server address login page is a valid Corporate email server login, for example.

Upon successful verification, a request is forwarded to the ground server 149 to verify the address entered is a valid corporate email server. This step is represented by another decision block (Block 510). This corresponds to the ground validation component of the whitelisting.

The ground server 149 is coupled to the email server 147 through the Internet. Upon successful verification in the air, the request is forwarded to the ground server 149 to verify if the address entered is a valid corporate email address. The ground server 149 then requests the login page of the corporate email server 147 using the address the passenger entered.

The ground server 149 at Block 510 thus requests the login page from the corporate email server 147 using the entered corporate email address. One or more tests are performed to verify the corporate email address, and one or more return metrics are generated. If the URL syntax is not validated, an error message is returned to the passenger at Block 512 and access is denied to the corporate email server 147.

One example test is for the page to contain a corporate email login form, wherein a response is sent to the aircraft server 162 which dynamically adds the corporate mail server address to the access control firewall rules. The dynamic whitelisting is temporary and can be set to expire via a number of techniques including static or dynamic timed lease expirations, event driven, or expiration at the end of flight, etc. It is also possible to automatically add temporary/dynamic whitelist servers to the static whitelist site list base on test criteria that could be resident on the ground sever 149 or the aircraft server 162.

Following a successful ground validation component at Block 510, the dynamic whitelist opens a temporary path in the firewall to the corporate email server 147 at Block 514. The passenger's Internet browser is then directed to the login page for their corporate email at Block 516. The process ends at Block 518. Alternatively, the ground server 149 may be bypassed and the ground verification is performed directly by the corporate email server 147. This same process could be used for dynamically whitelisting sites for applications other than email.

Many modifications and other embodiments of the invention will come to the mind of one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is understood that the invention is not to be limited to the specific embodiments disclosed, and that modifications and embodiments are intended to be included within the scope of the appended claims. 

1. A communications system for an aircraft carrying at least one person having a personal electronic device (PED), the communications system comprising: at least one wireless access device; an aircraft server in the aircraft cooperating with said at least one wireless access device for determining airborne validation of at least one ground server address entered via a corresponding PED; an air-to-ground transceiver in the aircraft cooperating with said aircraft server for communicating over an air-to-ground interface the at least one airborne validated ground server address; and at least one ground server on the ground for receiving the at least one airborne validated ground server address over the air-to-ground interface, determining ground validation of the at least one airborne validated ground server address, and providing ground access for the corresponding PED for which the entered at least one ground server address has both airborne and ground validation.
 2. The communications system according to claim 1 wherein said at least one wireless access device comprises at least one access point for providing a wireless local area network (WLAN) for each corresponding PED.
 3. The communications system according to claim 1 wherein said at least one ground server comprises at least one organization ground server having a firewall associated therewith; and wherein the at least one ground server address corresponds to said at least one organization ground server.
 4. The communications system according to claim 1 wherein said at least one ground server comprises at least one corporate ground server having a firewall associated therewith; and wherein the at least one ground server address corresponds to said at least one corporate ground server.
 5. The communications system according to claim 1 wherein each corresponding PED accesses a web-based prompt via said at least one wireless access device to enter a ground server address.
 6. The communications system according to claim 5 wherein the ground server address corresponds to a uniform resource locator (URL).
 7. The communications system according to claim 1 wherein said aircraft server determines airborne validation of the at least one entered ground server address by comparing to an airborne whitelist of accepted ground server addresses.
 8. The communications system according to claim 1 wherein said aircraft server determines airborne validation of the at least one entered ground server address by comparing to an airborne blacklist of rejected ground server addresses.
 9. The communications system according to claim 1 wherein the at least one entered ground server address corresponds to a uniform resource locator (URL); and wherein said aircraft server determines airborne validation by determining if the URL has a valid URL syntax.
 10. The communications system according to claim 1 wherein said aircraft server returns an error message to the PED when a ground server address associated therewith fails airborne validation.
 11. The communications system according to claim 1 wherein said ground server determines ground validation of the at least one airborne validated ground server address by comparing to a ground whitelist of accepted ground server addresses.
 12. The communications system according to claim 1 wherein said ground server determines ground validation of the at least one airborne validated ground server address by comparing to a ground blacklist of rejected ground server addresses.
 13. The communications system according to claim 1 wherein the at least one airborne validated ground server address corresponds to a uniform resource locator (URL); and wherein said ground server determines ground validation by determining if the URL has a valid URL syntax.
 14. The communications system according to claim 1 wherein said ground server returns an error message over the air-to-ground interface to the PED when an airborne validated ground server address associated therewith fails ground validation.
 15. The communications system according to claim 1 wherein said aircraft server maintains an airborne whitelist of accepted ground server addresses; and wherein said ground server dynamically updates the airborne whitelist over the air-to-ground interface.
 16. The communications system according to claim 15 wherein the dynamic updates to the airborne whitelist are temporary.
 17. The communications system according to claim 15 wherein the dynamic updates to the airborne whitelist expire at an end of a flight of the aircraft.
 18. The communications system according to claim 1 wherein the at least one ground server address corresponds to at least one email server address; and wherein said at least one ground server interfaces with an email server.
 19. A communications system for an aircraft carrying at least one person having a personal electronic device (PED) for exchanging emails outside the aircraft, the communications system comprising: at least one access point in the aircraft for providing a wireless local area network (WLAN) for the PED, with the PED accessing a web-based email prompt via the WLAN; an aircraft server in the aircraft cooperating with said at least one access point for determining airborne validation of at least one email server address entered by a corresponding PED via the web-based email prompt; an air-to-ground transceiver in the aircraft cooperating with said aircraft server for communicating over an air-to-ground interface the at least one airborne validated email server address; and at least one email server having a firewall associated therewith on the ground for receiving the at least one airborne validated email server address over the air-to-ground interface, determining ground validation of the at least one airborne validated email server address, and providing email access for the corresponding PED for which the entered at least one email server address has both airborne and ground validation.
 20. The communications system according to claim 19 wherein said aircraft server determines airborne validation of the at least one entered email server address by performing at least one of the following: comparing the at least one entered email server address to an airborne whitelist of accepted email server addresses; and comparing the at least one entered email server address to an airborne blacklist of rejected email server addresses; and if the at least one entered email server address corresponds to a uniform resource locator (URL), then determining if the URL has a valid URL syntax.
 21. The communications system according to claim 19 wherein said email server determines ground validation of the at least one airborne validated email address by performing at least one of the following: comparing the at least one entered email server address to a ground whitelist of accepted email server addresses; comparing the at least one entered email server address to a ground blacklist of rejected email server addresses; and if the at least one entered email server address corresponds to a uniform resource locator (URL), then determining if the URL has a valid URL syntax.
 22. The communications system according to claim 19 wherein said aircraft server maintains an airborne whitelist of accepted email server addresses; and wherein said email server dynamically updates the airborne whitelist over the air-to-ground interface to include the airborne validated email server address after ground validation.
 23. A method for operating a communications system for an aircraft carrying at least one person having a personal electronic device (PED), the communications system comprising at least one wireless access device in the aircraft, an aircraft server in the aircraft, an air-to-ground transceiver in the aircraft, and a ground server on the ground, the method comprising: operating the PED in the aircraft for entering at least one ground server address to the at least one wireless access device; operating the aircraft server in the aircraft to cooperate with the at least one wireless access device for determining airborne validation of at least one ground server address entered via a corresponding PED; operating the air-to-ground transceiver in the aircraft to cooperate with the aircraft server for communicating over an air-to-ground interface the at least one airborne validated ground server address; and operating the ground server on the ground to receive the at least one airborne validated ground server address over the air-to-ground interface, to determine ground validation of the at least one airborne validated ground server address, and to provide ground access for the corresponding PED for which the entered at least one ground server address has both airborne and ground validation.
 24. The method according to claim 23 wherein the at least one wireless access device in the aircraft comprises at least one access point for providing a wireless local area network (WLAN) for each corresponding PED.
 25. The method according to claim 23 wherein each PED accesses a web-based ground prompt via the at least one wireless access device to enter the at least one ground server address.
 26. The method according to claim 23 wherein the aircraft server determines airborne validation of the at least one entered ground server address by performing at least one of the following: comparing the at least one entered ground server address to an airborne whitelist of accepted ground server addresses; and comparing the at least one entered ground server address to an airborne blacklist of rejected ground server addresses.
 27. The method according to claim 23 wherein that at least one entered ground server address corresponds to a uniform resource locator (URL); and wherein the aircraft server determines airborne validation by determining if the URL has a valid URL syntax.
 28. The method according to claim 23 wherein the ground server determines ground validation of the at least one airborne validated ground server address by performing at least one of the following: comparing the at least one entered ground server address to a ground whitelist of accepted ground server addresses; and comparing the at least one entered ground server address to a ground blacklist of rejected ground server addresses.
 29. The method according to claim 23 wherein the at least one airborne validated ground server address corresponds to a uniform resource locator (URL); and wherein the ground server determines ground validation by determining if the URL has a valid URL syntax.
 30. The method according to claim 23 wherein the aircraft server maintains an airborne whitelist of accepted ground server addresses; and wherein the ground server dynamically updates the airborne whitelist over the air-to-ground interface to include the airborne validated ground server address after ground validation.
 31. The method according to claim 30 wherein the dynamic updates to the airborne whitelist are temporary.
 32. The method according to claim 23 wherein the at least one ground server address corresponds to at least one ground server address; and wherein the at least one ground server interfaces with an email server. 